perm filename TASKS[RDG,DBL] blob sn#642964 filedate 1982-02-02 generic text, type C, neo UTF8
COMMENT ⊗   VALID 00006 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	Given knowledge about SCORE, figure how to use SAIL.
C00003 00003	Dialogue: EMACS from E
C00006 00004	(Non)Corresponding commands: (E to EMACS)
C00009 00005	Goal - wrt Existing KBs
C00013 00006	II. Design a new KB (and expert system) modelled after existing KB/expert system:
C00014 ENDMK
C⊗;
Given knowledge about SCORE, figure how to use SAIL&
Nk <ESC> on SAIL - instead minimal prefix is sufficient.
	Also different control characters -- in line editor.
Directories are [prn,prp], not <User>.

EMACS is like E
	But character oriented, not line

TEX is like SCRIBE
	But n-pass each time
	Based on macros, not...

----
Learn E on UNIX, exploiting metap@!←efA→e←Z@q'β∪_y
AC]⊂@y'π=%
⎇5βπ&~(→	SC1←OkJhA≠β
&AMe=ZA
~)w⊃Ke∀XAiQ∀AC]C1←OSu∃dXAα0AW]←]fABA1←hA←_A
XA∧AESh↓CE←kPAKISQ←efA%\AOK9KeCX4∀QECMSGCY1rAErECEgQeCGi%]NDA→e←ZA∀RXAC9HA]←QQS]N↓CE←kPA≠β
&\~∃%ifAO=CXASLAi↑@	YKCe8DA≠¬π&\@↓)QSf↓oSYX↓EJAI=]JAa%KGK[∃CXXA	rACiQK[ai%]N~∃Q↑A[C@AgCY%K]hA→KCikIKfA←_A
@Q¬]HAQ=aKMk1YrXA!K]GJ0A←LA∃ISi←IfRA←9i↑A5βπ&\4∃)QJ↓KqaKIhXA*0AW]←]f@5KYKesi!S]NA¬E←kh↓E←iP↓csgi∃[f\~))QK\↓oJOY0Ao←eIrACE=khAKaGKai%←]f\QSJA⊃keS]≤AMSeMhAgi¬OJAi!KgJA]SYXA	JAakMQKH~)S]i↑↓iQJA	CGWOI←k]H8R~∀~)mK]QkCYYdXAaKIQCaf0AoJO1XAS]→KdAg=[KiQ%]NAe∀tA≠¬π&AMI←ZAM¬GifA¬E←kh↓'π∨%∀@Z~∃%\AaCIiSGk1CdXA%ifAe∃YCiS=\Ai↑↓'β∪_9|~∀Z4ZZ~∀4∃*tA∃≠βπ&↓SfAUUghAY%WJA
0AKqG∃ahA5βπ&A%fAGQ¬eCGi∃dXAe¬iQKd↓iQC\↓YS]J0A←eS∃]iKH8~∀~∃∧tA∨PZA∩A-]←nAQQChA∀ASfA∧AOK]∃eCXAAkea←MJAMk1XAgGIKK\A∃ISi←HXAek9]S]N↓←\AB↓YCeO∀~∃iS5JAgQ¬eS]N↓gsgi∃Z\@A%fA≠¬π&AC1XA←L↓iQKg∀ACfA]KYX}4∀~∃*hA3Kf8~∀~∃∧tA→KPA[JA%O]←e∀As←kHAG←[5K]hA¬E←khEGQCICGiKHA←eS∃]iKHλAM←d↓iQJA5←[K]P\~∀Q∃qC[S9S]NA∀OfAi∃CGQS9NACS⊃JXR~)ShAg∃K[fAQQJAE¬gSFA
←[[C9IfAM=dAKI%i←ef↓S]GYUIJ~∀%[←mS9NAiQ∀AGkeM←dX~(∪MS]⊃S]NAM←[JAMieS]≤X@~∀%gkEgQSiki%]NA←9JAgiIS]NA→←dAC9←iQKHX~∀∪MCmS]≤AC]H4∀∪Kq%iS]N8~∃βe∀AiQKMJAiQ∀AgC[∀AM←d↓≠βπL}~∀~)*tA3∃f\~∀4∃αtA¬eJAi!KeJA=iQKeL}~∀~)*tA3∃f@ZA5←mS]≤AiQJEa←S9hDXA⊃KMS]%]NAC9HAkg%]NA[¬Ge←f0@\\\4∀~∀xq∪]gKIhAYCQKdt~)∩AW]=nAiQ¬hA
A%fAYS9J[Ek→MKeK⊂\@Aβ1g↑XA	rAIK→S]Si%←\XA∃mKer↓YS]J↓Sf~∃∧Ae←n↓←LAG!CeCGQKef\A'Q←UYHA∩↓S]MKHAiQCPA≠β
&ASfEGQCICGiKHAEkM→KeKHλ}~∀~)*tA3∃f\~∀4∃αtA	kMMKIS]NA%fAI←9JAi↑↓MCGS1SiCi∀AGKeQCS\A=aKeCQS←]f8\\~∀8\\AQ∃]GJAQQJAm¬eS←kLAG←[5C]If↓M←dA5←mS]≤AC[←9NAYS9KfAo%YXAE∀AMCgQKdAS8A≠β
&v~∃]QKeK¬fA
OLAG←[5C]If0AoQS
PACM→KGhA	khA←9JAYS9JXACIJA[←IJAeCASH\~(|||~(~∀ZZ4~∃β]¬Y←OrhAeCi!KdAi!C\@E→e←ZA!KeJAQ↑AK]⊂A←LAACOJD0AeKC1Yr@E→e←ZA!KeJAQ↑Aa←%]hD\4∀~∀_Q≥←8Sπ←eIKga←9IS]Nαβ∂?7n;∪MR↓"∃β&yα⊗6~M$4Ts↔cQε≠#πK∞≠S↔Ibβ3';*aβ←'v#?]1αq984PJf;?&)α⊗6~Mα:⎇!βCπ>+⊃mβ∞s⊃βOzβ;=αt*bQβε∨⊗thRCK↔4K?WMε≠#πK∞≠S↔Ibβ3';*aβ←'v#?]1αq984PJfπMε∪↔≠?⊗)1α⊗l
∞MβFMβ;zαBJ⊗4J>VMπβπ∨⊗hh*≠'v!1αO.∪OS''+S∃1¬[?;∂*aβ↔[/∪eα~-"VJ∃ε{∂∂W⊗;∂∃bαε2⊃αC≠?K>K⊃β∞s⊃β∞≠/←π⊗!&t4T#?∂Wn+;Sπ&K?9↓FkW∂!ε+πO'/⊃β'9∧*6ε∞~↓5β'rα∃β7/≠Qβπg∪↔π∪Jβ/;?:α∃$4U#↔π∂FK;≥βn+∂#πvKO5↓jβ∂π3f+⊃α⊗$*ε∞!ε∪?S!π#'7↔~λ4(∀Ph*⊗6~Mβ'w≠↔KS~aα∃β␈3↔K←⊗KS↔MαCeβ&+≠πWg!$4(NC↔;∂*α⊗6ε≥→β7?⊗)βS←N#∪3↔∞∪3∃β∞s⊃βπ&CSπ⊗c∃βSzβ';∪O3'∪W∞aβWO/⊂4(ε↑;⊃α,jε∞Mε3C?5πβ3π∂*β←'S@β∪'≠6+K↔;"βC#'f{O?CGI1βπ ∧ε&NllW⊗.nDπ&N\[PhTYX∀≥~<⊗rε≥f&FT	T≥)z2εo\=αε⊗↑NF/∩∞Mε∞rλQPT,X_5~ε<≥bε∞<8W∂~∞8W6/,≥Bε6≥LW~ε≡@λ
⎇Xy(¬T⊃(_l≥I⎇β!((_]-≥≥λ≥
t~_;LM→(≠.]≥~+.9y(m;→<eD⊃30(:h~<d
[⎇AQQ(~≡h_(|;Y4L≥λ≠9,=_;Z.=r moving stuff around (αA, αC) - EMACS does it
	by (i) deleting and yanking back,
	or (ii) putting it into a buffer, then depositing that buffer.
EMACS - most commands can have 2 numerical parameters, E but 1.
	Default argument is the standard case: for both, usually +1 (eg for PAGE)
		[of course αL is simply 1L, NOT +1L (as that just <CR>)]
E - no backwards search (because of pages.)
EMACS based on 2 points (cursor and point) - E just has cursor.
E saves automatically on leaving a page, EMACS never saves (of course could twiddle
	it to do so automatically.)

Given this:
Mail at SAIL based on E, on SCORE on EMACS.  How similar, and how different?

Get to internals later: EMACS written on TECO, E in crude assembly code.
Goal - wrt Existing KBs

I. Incorporate a new concept, X, into an existing KB.

This can only work for certain types of domain concepts X:
(1) There is some domain concept Y s.t.
  (i) X is like Y
  (ii) much is known about Y
(2) Little is known about X, except
(3) How X is {like	    } Y.
 	     {different from}

The process would essentially involve:
	Finding all facts, F, which deal with Y.  From each such F, create an
analogous F', which deals with X. (I.e. Y:F :: X: F'.)


Examples:
	[Dendral world]
Esters like ketones
	[Molgen world]
EnzymesX like Restriction Enzymes
Expressed Regions (in DNA) like UnExpressed Regions.
Extrons are like Spacers (between-coding-region regions).
	[Chess worhd]
Rooks are like Bishops.
Rook pawns are like Bishop pawn.
	[Electronics world]
PNP junctions like NPN.
	[VLSI world]
AND gates are like OR gates.
vanNeumann machines like VLSI computers.
	[Computer science]
Recursion is like Iteration.
	[Mathematics]
Partial orderings are like total orderings.
Lattices are like Strict Hierarchies.
Groups are like Fields | Rings | ...

----
From Shortliffe:
	[Medical world]
<Trophic hormones>
Pituitary gland sends TCH to thyroid gland, which responds with T4,
	back to pituitary
Given this, consider how pituitary interacts with Adrenal:
(here it uses ACTH to Adrenal, and ? back)

?H from pituitary to skin. (no feedback)

Note that ?H shares much structure with ACTH (6 of 8-10 amino acids)

---
another use of analogy
for Oncology - visits are arranged horizontally, special medications vertically.
Then consider what next treatment should be, based on this history.
It should be analogous to earlier treatments, in similar situations...

------
Programme - find a few good fields, and X/Y pairs.
Important to be able to test result -- ie a running program (using Y),
and need to use X - together with known rules of X (which can be checked).

II. Design a new KB (and expert system) modelled after existing KB/expert system:

The abstraction here is (a theory of) EMYCIN.

Meningitis : Mycin :: Urinary tract diseases : ?
Meningitis : Mycin :: ?			     : SACON